Automated techniques have also been developed to assist in the estimation of demands using land use and population density data. These are similar to the Flow Distribution allocation methods except that the type of base layer that is used to intersect with the service layer may contain information other than flow, such as land use or population.

This type of demand estimation can be used in the projection of future demands; in this case, the demand allocation relies on a polygon layer that contains data regarding expected future conditions. A variety of data types can be used with this technique, including future land use, projected population, or demand density (in polygon form), with the polygons based upon traffic analysis zones, census tracts, planning districts, or another classification. Note that these data sources can also be used to assign current demands; the difference between the two being the data that is contained within the source. If the data relates to projected values, it can be used for demand projections.

Many of these data types do not include demand information, so further data conversion is required to translate the information contained in the future condition polygons into projected demand values. This entails translating the data contained within your data source to flow, which can then be applied using LoadBuilder.

After an appropriate conversion method is in place, the service layer containing the service areas and demand nodes is overlaid with the future condition polygon layer(s). A projected demand for each of the service areas can then be determined and assigned to the demand nodes associated with each service polygon. The conversion that is required will depend on the source data that is being used. It could be a matter of translating the data contained within the source, such as population, land area, etc. to flow, which can then be used by LoadBuilder to assign demands.

Depending on how the layers intersect, service areas may contain multiple demand types (land uses) that are added and applied to the demand node for that service polygon.